Release 10.1A: OpenEdge Development:
Progress Dynamics Web Development Guide

Object qualification

Qualification in the DHTML client is quite different from the GUI client. Because of the way JavaScript works, all logic is associated with the page—not individual objects. Therefore, a client logic API call does not have a run-time association with the object that the code is associated with during design time. (Thus, the “self” qualifier would not be useful and is not supported in the DHTML client.)

Unqualified names

You should only use qualified names with DHTML client code. One reason for this recommendation is that the DHTML client cannot discriminate between different occurrences of the same data field. Therefore, unqualified names affect every occurrence of the data field on the page.

Note: The DHTML client does not support unqualified names at the container level.

Qualified instance names

The basic form of qualification in the DHTML client uses the following syntax:

objectname.fieldname

Here, objectname is the browse or viewer instance name and fieldname is a field in that object. For example:

orderfullb.custnum customerviewv.name

Qualification with the browse keyword

You can use the browse keyword to specify the browse associated with a particular WDO. The syntax is:

wdoname.browse.fieldname.

Here, wdoname is the data source name, browse is a keyword, and fieldname is a column in the browse object for that WDO. For example:

customerfullo.browse.custnum